Method, apparatus and system for hosting information exchange groups on a wide area network

ABSTRACT

A method and system for hosting information exchange groups on a wide area network is disclosed, using various tools for promoting topical organization and self-evolution of the information exchange groups, and of a system of information exchange groups. These tools include methods for providing user rating of posts within the exchange group, for rating and ranking users of the exchange group, for rating and ranking links to related information pages and especially to related exchange groups operating according to the methods of the invention, and for continuously updating rating and ranking information. Additionally, methods are provided for users to found exchange groups, to filter information in exchange groups according to specified user preferences, and to protect private information from inadvertent disclosure to other users of the exchange group.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a divisional of U.S. patent application Ser. No.09/648,474, filed Aug. 21, 2000, which is a continuation-in-part of U.S.patent application Ser. No. 09/548,804, filed Apr. 14, 2000, nowabandoned, and claims benefit of U.S. Provisional Patent Application No.60/129,485, which was filed Apr. 15, 1999, each of which are herebyincorporated by reference in their entireties.

BACKGROUND OF THE INVENTION

1. Field of the Invention

The present invention relates to methods for exchanging and locatinginformation on computer networks, and more particularly, to a method andsystem for hosting information exchange groups on a wide area network.

2. Description of the Related Art

Wide area networks, such as the Internet, provide a vast and growingsource of information to a large and growing number of users on demand.One of the great advantages of exchanging information on a wide areanetwork is that users, and groups of users, may readily exchangeinformation with one another, both contemporaneously and at differenttimes. However, the quantity, dynamics and decentralized nature ofinformation on the Internet and other factors create obstacles to theexchange of information among the users.

Various ways of exchanging information within groups of users, such asinformation exchange groups are known in the art. For example, Web basedbulletin boards, “usenet” news groups, and chat rooms are forms of priorart information exchange groups. Prior art information exchange groupsdo not realize the benefits and advantages possible in consideration ofthe Internet, the World Wide Web, Internet browsers, and human behavior.Prior art information exchange groups do not provide a systematic methodfor discriminating between desired and undesired information. Therefore,prior art information exchange groups contain limited quantities ofdesired information, which tends to be randomly interspersed within amuch larger collection of undesired information having little or noinformation value.

For example, prior art information exchange groups are intruded upon byadvertisements and deluged by inappropriate posts and arguments amongposters. Knowledgeable users, i.e., “experts,” on a particular topic arefrequently unavailable, thereby limiting the amount of usefulinformation that can be obtained. Other problems that exist include, forexample, the inability of these groups to be located by end users, thelack of specificity of the topics discussed, or the lack ofparticipation in the group by all but a fraction of wide area networkusers due to the complexity of locating a group with pertinentdiscussion topics and the complexity of reading and participating in theposting. Further, the nature of the groups, such as chat rooms, detersuser participation for a variety of reasons. For instance, users ofprior art groups, such as chat rooms, are subject to a loss ofanonymity. If the user desires to be contacted, the user must post hisemail address. Frequently, users' email addresses are collected forcommercial use, and the user is then subjected to unwanted contact fromunrelated sources. Additionally, prior art groups do not effectivelysupplement user communications with related information, such as a listof hyperlinks to relevant sites. In addition, prior art groups do notfacilitate the use or direct exchange of audio or visual information.Prior art information exchange groups do not provide users a way toconveniently create or join an information exchange group, for example,a chat room, wherein the user's e-mail address is protected from otherusers and from unwanted commercial use. Also, prior art groups do notprovide for control by the users of the scope of information exchangedwithin the information exchange group. For the foregoing reasons,information exchange groups are not as widely used as they could be, norhas their full potential been realized.

Therefore, a need exists to provide for the operation of informationexchange groups on a wide area network that overcomes the limitations ofthe prior art.

SUMMARY OF THE INVENTION

The present invention provides a system and method for hosting a newtype of information exchange group, herein called a Webroom, on a widearea network, such as the Internet. A Webroom is a species ofinformation exchange group, comprising a computer-implemented, topicallyorganized self-evolving exchange group on a wide area network, accordingto the present invention. The system and method provides Webrooms withproperties and features for harnessing the power of the Internet and adistributed user community to build information exchange groups, andsystems of interlinked groups, with superior quantity and quality ofinformation content, and superior organization of information by topic.The method and system provides for user participation and user feedbackthat rewards the gathering and dissemination of useful and desiredtopical information within Webrooms, while discouraging and eliminatingunwanted or less useful information. The system additionally providesother features for attracting users and encouraging user participation.

Thus, the system and method provides for promotion of Webrooms by apowerful network effect. That is, as information content and number ofparticipating users of a Webroom grows, the Webroom becomes more likelyto attract additional users and to contain more useful information. Anadditional advantage is that the operating cost of hosting a Webroom,after the initial set-up cost, is essentially limited to the systembandwidth and storage needed to accommodate growth in usage, becausesubstantially all of the Webroom content is provided by the subscribinguser community.

The system and method make use of various software-implementedprocesses, or “tools,” to achieve the advantages described above.Underlying these tools is a software engine for enabling users to easilycreate their own topical Webrooms, and to peruse, post and evaluateinformation within Webrooms. A first tool rewards users, or groups ofusers, who establish Webrooms (such users being called “founders”) byreferring traffic from the Webroom Web site to a Web site of thefounders' choice. A second tool rewards users who refer other users tothe Webroom Web site in the same manner. A third tool ranks and filtersinformation presented on the site based on statistical user evaluationand use data, and user specified preferences. A fourth tool similarlyranks and filters information sources, such as contributing users andrelated Web Sites or Web Pages. A fifth tool provides users of a Webroomwith anonymous messaging, or chat room capability. A sixth tool providesuser protection filters, especially useful for protecting child users.

The system and method implements the above tools using a graphical userinterface having novel features. For example, the graphical interfacepresents messages in threaded or unthreaded format, according to theuser's selection using a toggle button. Other graphical features includea tolerance bar used for information filtering according to userpreferences, and pop-up or pull-down lists of related Web pages or otherinformation sources.

A more complete understanding of Webrooms will be afforded to thoseskilled in the art, as well as a realization of additional advantagesand objects thereof, by a consideration of the following detaileddescription of the preferred embodiment. Reference will be made to theappended sheets of drawings which will first be described briefly.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1A is a block diagram illustrating a computer system for providingWebrooms according to the present invention.

FIG. 1B is a block diagram illustrating an alternative embodiment of acomputer system for providing Webrooms according to the presentinvention, and further illustrating some features of Webrooms accordingto the preferred embodiment of the invention.

FIG. 2A is a concept diagram illustrating features of an informationexchange group according to the prior art.

FIG. 2B is a concept diagram illustrating in more detail features of aninformation exchange group according to the prior art.

FIG. 3A is a concept diagram illustrating features of a Webroom.

FIG. 3B is a concept diagram illustrating features of a Webroom in moredetail. FIG. 4 is a flow chart illustrating a method for founding aWebroom.

FIG. 5A is a flow chart illustrating a method for operating a Web pagemenu for a Webroom.

FIG. 5B is a flow chart illustrating a registration and login method fora Webroom.

FIG. 5C is an illustration of an exemplary display of a Web page fordisplaying posts grouped according to a subject thread, with variousWebroom menu objects.

FIG. 5D is an illustration of an exemplary display of a Web page fordisplaying posts that are not grouped according to a subject thread,with various Webroom menu objects.

FIG. 6A is a flow chart illustrating a method for providing users anoption to view, respond to, and individually rate information postsstored in a Webroom memory.

FIG. 6B is an illustration of an exemplary display of a Web pageprovided with features for providing users an option to rate posts.

FIG. 6C is a flow chart illustrating further details of a method forproviding users an option to individually rate information posts storedin a Webroom memory.

FIG. 6D is an illustration of a data structure for rating data receivedfrom Webroom users.

FIG. 7 is a flow chart illustrating a method for providing users anoption to rate related Web pages for which links are on a Webroom pagemenu.

FIG. 8 is a flow chart illustrating a method for providing users anoption to rate a related Webroom pages for which links are on a Webroompage menu.

FIG. 9 is a flow chart illustrating a method of performing Webroommaintenance.

FIG. 10A is a flow chart illustrating a method for rating and rankingusers of Webrooms.

FIG. 10B is an illustration of a data table containing exemplary userrating data.

FIG. 10C is an illustration of an exemplary display of user ratinginformation on a Web page.

FIG. 11A is a flow chart illustrating a method for ranking related Webpages for which links are on a Webroom page menu.

FIG. 11B is an illustration of a data table containing exemplary Webpage rating and ranking data.

FIG. 11C is an illustration of an exemplary display of Web page ratingand ranking information on a Web page.

FIG. 12A is a flow chart illustrating a method for ranking relatedWebroom pages for which links are on a Webroom page menu.

FIG. 12B is an illustration of a data table containing exemplary Webroompage rating and ranking data.

FIG. 12C is an illustration of an exemplary display of Web room pagerating and ranking information on a Web page.

FIG. 13A is a flow chart illustrating a method for receiving preferenceinformation from a Webroom user, and filtering posts displayed on theuser's Webroom page according to threshold criteria specified in thepreference information.

FIG. 13B is an illustration of an exemplary display of a Web page forcollecting user preference information.

FIG. 14 is a flow chart illustrating a method for providing a privateWebroom.

FIG. 15 is a flow chart illustrating a method for providing protectionof a user's private information using terminal control

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENT

The present invention satisfies the need for a method and system forproviding an information exchange group that adds new functions andimproves upon prior art information exchange groups. In the detaileddescription that follows, like element numerals are used to describelike elements illustrated in one or more figures. Various terms andacronyms are used throughout the detailed description, including thefollowing:

Application. Within the context of computer hardware and software, anapplication is a set of one or more computer programs that performs afunction when executed within a computer hardware device. If the set iscomprised of plural programs, the programs are coordinated to perform afunction together; such programs may also perform other functionsindividually. Similarly, a program may be comprised of plural modulesthat perform certain functions individually and other functions whencombined in various ways.

Client-Server. A model of interaction in a distributed system in which aprogram at one site sends a request to a program at another site andwaits for a response. The requesting program is called the “client,” andthe program which responds to the request is called the “server.” In thecontext of the World Wide Web (discussed below), the client is a “Webbrowser” (or simply “browser”) which runs on a computer of a user. Theprogram which responds to browser requests by serving Web pages iscommonly referred to as a “Web server.”

Cookies. A technology that enables a Web server to retrieve informationfrom a user's computer that reveals prior browsing activities of theuser. The information item is stored on the user's computer (typicallyon the hard drive) is commonly referred to as a “cookie.” Many standardWeb browsers support the use of cookies.

Distributable application. An application coded in a language, such asthe JAVA language developed by Sun Microsystems, Inc., such that theapplication may be distributed over a wide area network, such as theInternet, and be successfully executed on a variety of computer hardwaremodels running various operating systems.

Flame. In the context of an information exchange group, a flame is auser message of an offensive nature.

HTML (HyperText Markup Language). A standard coding convention and setof codes for attaching presentation and linking attributes toinformational content within documents. (HTML 2.0 is currently theprimary standard used for generating Web documents, although it shouldbe appreciated that other coding conventions could be used within thescope of the present invention.) During a document authoring stage, theHTML codes (referred to as “tags”) are embedded within the informationalcontent of the document. When the Web document (or HTML document) issubsequently transferred from a Web server to a browser, the codes areinterpreted by the browser and used to parse and display the document.Additionally, in specifying how the Web browser is to display thedocument, HTML tags can be used to create links to other Web documents(commonly referred to as “hyperlinks”).

HTTP (HyperText Transport Protocol). The standard World Wide Webclientserver protocol used for the exchange of information (such as HTMLdocuments, and client requests for such documents) between a browser anda Web server. HTTP includes a number of different types of messages thatcan be sent from the client to the server to request different types ofserver actions. For example, a ‘GET’ message, which has the format GET<URL>, causes the server to return the document or file located at thespecified URL.

Hyperlink. A navigational link from one document to another, or from oneportion (or component) of a document to another. Typically, a hyperlinkis displayed as a highlighted word or phrase on a Web page that can beselected by clicking on it using a mouse or other pointing device tojump to the associated document or documented portion.

Hypertext System. A computer-based informational system in whichdocuments other types of computer files are linked together viahyperlinks forming a user-navigable “Web.”

Information Exchange Group. A general term encompassing a particular setof protocols or rules for information sharing, together with aparticular set of shared information or data collected or generatedunder the associated rules and protocols, for use by users (or othersources) contributing information to, or accessing information in, theshared set of information. As implemented on the Web, informationexchange groups include the entire Web and subgroups located on the Web,such as newsgroups, bulletin boards, message boards, chat rooms, and“Webrooms.” Webrooms are further described in the detailed descriptionbelow, and in the co-pending applications referenced therein.

Internet. A collection of interconnected (public and/or private)networks that are linked together by a set of standard protocols (suchas TCP/IP and HTTP) to form a global, distributed network. (While thisterm is intended to refer to what is now commonly known as the Internet,it is also intended to encompass variations which may be made in thefuture, including changes and additions to existing standard protocols.)

Spam. In the context of an information exchange group, spam is anyunwanted user message or messages of a commercial nature.

URL (Uniform Resource Locator). A unique address which fully specifiesthe location of a file or other resource on the Internet. The generalformat of a URL is protocol://machine address:port/path/filename. Theport specification is optional, and if no port is specified, the browserdefaults to the standard port for whatever service is specified as theprotocol.

World Wide Web (“Web”). Used herein to refer generally to both (i) adistributed collection of interlinked, user-viewable Web pages and otherlinked data and distributable applications that are accessible via theInternet, and (ii) the client and server software components whichprovide user access to such documents using standardized Internetprotocols. Currently, the primary standard protocol for allowingapplications to locate and acquire Web documents is HTTP, and the Webpages are encoded using HTML. However, the terms “Web” and “World WideWeb” are intended to encompass future markup languages and transportprotocols which may be used in place of (or in addition to) HTML andHTTP.

Web Page. A hypertext file or document that is encoded using a languagesuch as HTML for viewing on a client computer using a browserapplication. A Web page may include visible components, such as text,images, hyperlinks, and a background, and/or invisible components, suchas meta tags and formatting instructions. In comparison to the term “Webpage,” the more general term “page” encompasses many other types ofcomputer files that are not necessarily encoded for viewing using abrowser, e.g., text files, bit-maps, audio files, and so forth.

Web Site. A computer system that serves informational content over anetwork using the standard protocols of the World Wide Web. Typically, aWeb site corresponds to a particular Internet domain name, such as“electronsearch.com,” and includes the content associated with aparticular organization. As used herein, the term is generally intendedto encompass both (i) the hardware/software server components that servethe informational content over the network, and (ii) the “back end”hardware/software components, including any non-standard or specializedcomponents, that interact with the server components to perform servicesfor Web site users.

The foregoing definitions are not intended to limit the scope of thepresent invention, but rather are intended to clarify terms that arewell understood by persons having ordinary skill in the art, and tointroduce new terms helpful for describing the present invention. Itshould be appreciated that the defined terms may also have othermeanings to such persons having ordinary skill in the art. These andother terms are used in the detailed description below.

Referring to FIG. 1A, a block diagram is illustrated of a wide areanetwork employing a method and system according to the invention. It isanticipated that the present information delivery system 100 operateswith a plurality of computers which are coupled together on a wide areanetwork, such as the Internet 102, or other communications network. FIG.1A depicts a network that includes at least two user computers 120 and130 that communicate with a Webroom Web host 110 though communicationlinks 104 that include the Internet 102. The user computers 120 and 130may be any type of computing device that allows a user to interactivelybrowse Websites, such as a personal computer (PC) that includes a Webbrowser 132 (e.g., Microsoft Internet Explorer™ or NetscapeCommunicator™). Suitable user computers, e.g., user computer 130equipped with browsers 132, are available in many configurations,including handheld devices (e.g., PalmPilot™), personal computers(PC's), laptop computers, workstations, television set-top devices,multi-functional cellular phones, and so forth. The Webroom Web host 110includes a server computer 112 running Webroom Web server application114 and capable of selectively delivering and receiving information,such as Web pages 126 and 136, to and from the user computers 120 and130 using a protocol, such as HTTP. Webroom Web host 114 uses database116, containing Webroom data, while performing functions according tothe present invention. Typically, Webroom Web server 114 is anapplication coded in a programming language, such as C or C++, and iscustomized to run on server 112. Webroom Web server 114 may additionallyincorporate a database engine, such as a SQL Server™ engine fromMicrosoft Corporation or Oracle™ database engine, as part of itsarchitecture. Using user computers 120 and 130, user 128 and user 138,respectively, may communicate to one another by sending commands anddata using browsers 122 and 132. User communication data is preferablyaccessible on Web pages 126 and 136, displayed on displays 124 and 134.Web pages 126 and 136 are preferably Web room pages.

Referring now to FIG. 1B, a block diagram illustrates an alternativeembodiment of a computer system for providing Webrooms according to thepresent invention, and some features of Webrooms according to thepreferred embodiment of the invention. In the alternative embodiment, inaddition to the components and features discussed previously inconnection with FIG. 1A, the system includes Web site 140. Web site 140includes Web server 142 accessing a database of Web pages 144, and otherelectronic files containing information of various types, such asdistributable applications and text files. Web pages 144 may be viewedon a display or a user computer, e.g., display 124 of user computer 120.For example, Web page 126 or other electronic files may be presented ondisplay 124 by a suitable application program residing on user computer120, such as browser 122, or by a distributable application provided touser computer 120 by Web server 142. It should be appreciated that manydifferent user computers, many different Web servers, and many differentsearch servers of various types may be communicating with each other atthe same time.

Web pages are generally requested by communicating an HTTP request froma browser application, such as browser 132. The HTTP request includesthe Uniform Resource locator (URI) of the desired Web page, which maycorrespond to a Web page 136 stored at a destination Web site, such asWebroom Web host 110, or Web site 140. The HTTP request is routed to theWebroom Web host 110 or Web site 140 via the Internet 102. The WebroomWeb server 114 or server 142 then retrieves the requested Web page,identified by a URL, from database 116 or 144 and communicates the Webpage across the Internet 102 to the browser application 132 or 122. TheWeb page may be communicated in the form of plural message packets asdefined by standard protocols, such as the Transport ControlProtocol/Internet Protocol (TCP/IP), although it should be appreciatedthat communication using other protocols would be within the scope ofthe invention.

To exemplify features of Webrooms, FIG. 1B illustrates a Web page 126,containing information 121 and a hyperlink 127 to Webroom Web page 136,delivered to user computer 120 for viewing on display 124 using browser122. At the same time, a Web page comprising Webroom Web page 136 isdelivered to user computer 130 and displayed on display 134 usingbrowser 132. Webroom Web page 136 contains posts 133 pertaining to topic131, and a top list 135 including hyperlink 137 to Web page 126. Topic133 pertains to information 121 on page 126, and thus Web page 126 maybe of interest to someone viewing Webroom Web page 136. If so, hyperlink137 may be selected which will cause server 142 to send a copy of Webpage 126 to user computer 130. Similarly, Webroom Web page 136 may be ofinterest to someone viewing Web page 126, and if so, hyperlink 127 maybe selected. Selecting hyperlink 127 causes Webroom Web server 112 tosend a copy of Webroom Web page 136 to user computer 120. In connectionwith the request, Webroom Web server application preferably records theidentity of the referring page, i.e., the page on which hyperlink 127 islocated, for later use in determining placement of hyperlink 137 on toplist 135, relative to other hyperlinks in the top list.

A principle advantage of the present invention is that it tends toprovide information exchange groups that are topically organized andself-evolving. These features are illustrated and compared to prior artgroups in FIGS. 2A-3B. FIG. 2A illustrates numerous prior artinformation exchange groups 300 located in an Internet space 102. Eachprior art group 300 contains information posts 312, and a topic 322,such as topics 322 a and 322 b. Each post 312, shown in FIG. 2B, isreceived from a contributing user 310 on the Internet or other wide areanetwork. Each post has a greater or lesser degree of relevance to thegroup's topic. The posts 312 are stored in one or more memories 320connected to Internet 102. Memory 320 may be distributed over one ormore memory devices, and is managed by a server device according tomethods known in the art. To users 310, the posts 312 appear as objectson a Web page displayed on each user's client computer by a groupserver. Typically, the group server provides users 310 with anopportunity to receive, read, and respond to selected posts 312, andrecords a sequence of responses for each posting.

In prior art groups 300, the information posts are not organizedaccording to their relevance to topic 322. This lack of contextualinformation is diagrammed in FIG. 2B as a random distance between eachof posts 312 and the topic 322. Some of the posts 312 may be connectedby a thread 340, which is essentially a record of a sequence of postsand responses. For example, a first post by a first user, and a secondpost by a second user, sent in response to a first post, are linked by asingle thread. A third post, posted in response to the first message,would begin a second thread between the third post and the first post.In the alternative, a third post in response to the second post wouldcontinue the first thread from the first post, to the second post, andthen to the third post. Any number of posts may be connected, or“threaded,” in this manner. Although threading provides a limited amountof self-organizing information, in that the posts on a thread are morelikely to relate to the same topic, prior art groups 300 do not providea way for users to rate the relatedness of single posts or threadedposts to any particular topic. Consequently, information is randomlydistributed among the posts 312, making searching for particular topicalinformation a haphazard process for users 310.

Prior art groups 300 also do not provide for organizing links to otherinformation exchange groups, Web pages, or other information locatedwithin the Internet space 102. Although some of the posts 312 may.contain references 330 to external information, the references 330 arerandomly scattered throughout posts 312, which posts 312 are themselvespoorly organized with respect to the group topic 322. Because of theirpoor organizing properties, prior art groups 300 do not encourage orreward users 310 for submitting informative and relevant posts. Forexample, a user 310 is less likely to invest time and effort intosubmitting information, because the user's post will quickly become lostand forgotten. Hence, prior art groups 300 have tended to evolve intorecreational-oriented communities with relatively little usefulinformation content compared to Web sites operated by organizedentities.

In contrast, an information exchange group according to the presentinvention (a Webroom) has self-evolving properties that provide fortopical organization within the Webroom, and within a structurecomprised of multiple interconnected Webrooms. These properties areillustrated in FIGS. 3A and 3B. In FIG. 3A, a portion of a system 302comprised of multiple interconnected Webrooms is shown. Webrooms 301 a,301 b, 301 c, 301 d, and 301 e, residing in an Internet space 102, areinterconnected with multiple links 326 and 326′. Any particular Webroom,for example, Webroom 301 d, may have one or more paired links,comprising a link to an external Webroom, such as shown between Webrooms301 d and 301 b. Each paired link comprises a link to an external site326 and a link back from the site 326′. As seen from the perspective ofWebroom 301 b, 326′ is the link to the external site and 326 is thecomplementary link back. Webrooms may have one-way links, such as link326 shown between Webrooms 301 a and 301 e, links to other Web pages 324such as shown from Webroom 301 a, links to prior art information groups300 f such as shown from Webroom 301 d, and links to any other objecthaving a network address. Each link 326 and 326′ is preferably ahyperlink.

Webrooms are preferably provided with any number of defined topics, suchas topics 322 a, 322 b, 322 c, 322 d, and 322 e. The topics may be atany level of particularity or generality, and may be capable of groupinginto any number of, and any levels of, subject groups, such as thesubject groups illustrated by the areas 340 a and 340 b. Subject groupsmay be overlapping, or non-overlapping. In FIG. 3A, the subject groups340 a and 340 b are shown as overlapping with respect to topics 322 band 322 d. The configuration illustrated in FIG. 3A might arise, forexample, if subject area 340 a is “dogs,” subject area 340 b is “cats,”and topic 322 b is “pet toys” and 322 d is “veterinary medicine.”

It should be understood that the self-evolving interconnections of thepresent invention make it unnecessary to objectively define any subjectareas. Rather, subject areas are conceptual constructs that arise fromthe nature of the interconnected structure provided by the presentinvention. Webrooms with the most closely related topics are directlylinked, and more distantly related Webrooms are linked by a number ofintervening links, the number of links being inversely proportional tothe relatedness of connected Webrooms. That is, more closely relatedWebrooms are connected by fewer links. Thus, any particular subjectarea, although not objectively defined and having no distinct boundary,will nonetheless be perceived as a collection of Web rooms that areclosely linked to each other. The present invention provides a method,as described in detail below, for providing Webrooms with inherent,self-evolving properties ensuring that only Webrooms with closelyrelated topics will be directly linked to each other, and that eachWebroom will grow or evolve links to all Webrooms having closely relatedtopics. As a result, the topically organized, interconnected Webroomsystem 302 is capable of emerging from the participation of manyindividual, self-interested users, and evolving to higher levels ofinformation and organization without the application of any externalorganizing agent or externally applied function.

The present invention also provides for topical, self-evolvingorganization within a Webroom defined by a topic, as illustrated in FIG.3B. Webroom 301 a, like prior art groups 300 discussed above, has adefined topic 322 a, receives numerous information posts 312 from users310 and stores them in a memory 320. Users 310 may receive, read, andrespond to any of posts 312, and posts may be threaded, as shown withthread 340, or unthreaded. Unlike prior art groups 300, however, Webroom301 a ranks each post 312 according to its relevance to topic 322 a.This ranking is illustrated by the concentric orbits 322, each orbitrepresenting a discrete level of relevance to topic 322 a. It should beunderstood that for simplicity, only two orbits 322 are illustrated, buta Webroom may have any number of orbits, and typically will havenumerous orbits. Alternatively, posts 312 may be ranked according to anarithmetic system that does not use discrete relevance levels, andfurther may be ranked with respect to numerous ranking categories.Various ranking schemes are further described in more detail later inthe specification.

Similarly, users 310 of Web room 301 a are preferably ranked accordingto various schemes. FIG. 3B illustrates an orbit system, having onefounding user 314 on a founder's orbit, a number of users 310 on anexpert orbit 316, and a greater number of users 310 on a contributinguser orbit 318. Only three orbits are shown for simplicity, but atypical Webroom will have more numerous orbits, or a more sophisticatedranking scheme, which is described in more detail later in thespecification, Users are provided an option to rate selected posts 312.Rating information pertaining to selected posts 312 is received fromusers according to methods discussed below, and used to rank the posts312 and users 310. As a result of the ranking scheme, users compete fora favorable position for their posts with respect to topic 322 a bysubmitting posts of superior information value, by providing links todesired information resources, and by providing rating information.

An advantage of the invention is that users are rewarded forcontributing high quality information by achieving highly rankedpositions. In general, one skilled in the art will recognize that theprominence and recognition associated with a high ranking among a groupof many users may readily be used to bring benefits of many types, e.g.,to draw traffic to a commercial site. Thus, by its ranking and rewardsystem, the Webroom 301 a tends to attract more desirable and relevantinformation pertaining to topic 322 a, and ranks the best informationhighly so it may easily be found by users. This in turn attracts moreusers, who in turn provide still more and better information and assistwith organizing the Webroom, and so forth. Additionally, ranking usersmakes it easy to identify experts and request information from them.Thus, by ranking information and users, Webrooms, such as Webroom 301 a,tend to promote themselves and grow to become increasingly more usefulinformation resources through a powerful network effect.

Like prior art groups 300, Webrooms, such as the illustrated Webroom 301a, also may have posts with external references 330. However, thepresent invention provides a method for providing, organizing, andranking links to outside references, as described above in connectionwith FIG. 3A. In FIG. 3B, one such pair of links 326 and 326′ isillustrated to a founder's page 324 a. A founder's page is a Web page orother document designated by a founding user 314, as indicated by thedashed line 315. By providing a link to a site designated by user 314,and ranking the link highly or displaying it prominently, user 314 isrewarded for investing the time and effort required to found Webroom 301a. Similarly, other users 310 may be rewarded for contributing to theWebroom 310 a, for directing traffic to a Webroom through a linked Webpage, for sponsoring the Webroom host, or for other desired behavior, bybeing permitted to designate or nominate a link to another Web site,such as 324 b. External sites preferably have a return link 326′ to theWebroom 301 a, and the usage of each return link 326′ is preferablymeasured. External sites with links to and from Webroom 301 a preferablyinclude other Webrooms, as illustrated in FIG. 3A and discussed above.

Like posts and users, links 326 are preferably ranked using rating dataprovided by users 310. Additionally, it is preferable to include theamount of Web traffic provided by a site's return link 326′ to theWebroom 301 a as a ranking factor, to encourage and promote Webroomtraffic. Commercial factors, such as payment and contractual terms, mayalso be considered in ranking, preferably using a weighted system asdescribed in the co-pending U.S. patent application, Ser. No.09/548,803, “METHOD AND SYSTEM FOR SEARCHING A WIDE AREA NETWORK,” filedApr. 14, 2000, which application is specifically incorporated herein, inits entirety, by reference. In this manner the costs of hosting Webroomsmay be defrayed, and a profit motive for hosting and promoting Webroomgrowth may be provided. However, to ensure that external sites with themost closely related topics and best information receive the highestranked links, thereby optimizing the topical organization andinformation content of the system 302, the highest importance in therating scheme is preferably assigned to topical rating information.

The general characteristics of Webrooms, and systems of Webrooms, arepreferably achieved on a wide area network, such as the Internet, byimplementing the method steps of the invention using computer hardware,network connections, and software according to techniques known in theart. Various method steps are illustrated in FIGS. 4-15, beginning withsteps for founding a Webroom illustrated in FIG. 4.

It is preferable to the harness the power of a volunteer user base forfounding Webrooms, for the same reason it is preferable to harness avolunteer user base for providing rating data. Namely, the vast numberor users connected to the Internet comprises a resource of enormous sizeand power, and volunteers do not need to be paid. In some cases, it maybe desirable to pay or contract with founders to found Webrooms, or somecombination of paid contractors and unpaid volunteers may be used forfounding Webrooms. The method illustrated in FIG. 4 may be adapted foruse with these various types of founders.

The process begins by issuing prospective founders an invitation tofound a Webroom at step 402. An invitation is extended by variousadvertising techniques known in the art, for example, using a banneradvertisement on a search engine site, or by any mode of communication.However, it is preferable to extend invitations by direct messaging topersons searching for a Webroom using a search method, such as disclosedin the previously referenced U.S. patent application, Ser. No.09/548,803. An invitation is preferably extended when a user is unableto locate a Webroom for a particular topic, because no Web room havingthat particular topic exists. Such persons are more likely to beinterested in the topic and in Webrooms, and therefore are more likelyto accept an invitation to found a Webroom covering the particulartopic. Additionally, the invitation/acceptance process can readily behandled automatically using techniques known in the art, without anyneed for a human on the Webroom host side, thereby reducing the cost offounding Webrooms.

At step 404, the founder applicant applies for founder status and theapplicant's application is received, beginning a dialog between theapplicant and the Webroom host. An applicant may apply by sending amessage to the Webroom host, which may be comprised simply of a mouseclick or other simple response, and preferably includes, or is linkedto, other application data including the identity of the applicant andthe applicant's client terminal, name and electronic addressinformation, the topic, and selected founder resume information, such asother Webrooms the applicant has founded. If the applicant is already aregistered Webroom user, most of this information is preferably alreadystored in a user database 406, from which it may readily be retrieved.The Webroom processes the application information at step 408 to ensurethe application is complete, and stores new information in user database406 for later use.

The topic submitted by the applicant, or otherwise associated with theapplication, is preferably processed at step 410 for recognition of thelanguage the topic is submitted in, identification of misspellings, andidentification of non-dictionary words, and other topic problems. Forexample, the host may screen for words deemed too offensive to appear astopics, or words that are otherwise likely to be used for Webrooms thatthe Webroom host does not desire to host. However, it is anticipatedthat in general, topic processing is preferably limited to identifyingcommon spelling defects, semantic inconsistencies, and duplicate topics,in order to avoid placing unnecessary restrictions on topic creation andto facilitate the founding process. Elimination of undesirable andunused Webrooms takes place later during the Webroom cycle, by auser-driven rating process described in more detail later in thespecification. Topic database 424, and/or a database containingdictionary information (not shown) may be consulted during the topicprocessing step.

If a problem with the topic is identified during processing, the topicis deemed not qualified at decision step 412, and the topic problems arepresented to the applicant at step 414. Depending on the nature of thetopic problems, the applicant is invited to correct the problems andresubmit the topic for processing at step 410, or to accept the topic asis, which may be appropriate, for example, if the topic includes a wordor phrase that is not in the system dictionary database, as may occurwith new slang terms. In such cases, the applicant is preferably invitedto supply a meaning for the undefined term, so that the term may beadded to the topic and dictionary databases with a defined meaning. Thetopic is then preferably reprocessed at step 410 using the correctedterms and/or new definitions.

If the topic is deemed qualified at step 412, then at step 416, thetopic is tested to determine if a Webroom with the same topic alreadyexists. Unlike many prior art information exchange groups, it ispreferable to prevent the formation of duplicate Webrooms, i.e., two ormore Webrooms having essentially the same topic, to promote topicalorganization within a Webroom system, and to concentrate all possibleinformation pertaining to a topic within a single Webroom. Thus, inperforming testing for duplicate Webrooms, it is preferable to check forand prevent founding of Webrooms with synonymous topics. For example,two Webrooms, one with the topic “quadruped bovines”, and one with thetopic “four-legged cows” would be undesirable. At the same time,overlapping, partially synonymous topics are permissible and often arisebecause of a genus-species relationship, for example, “Jersey cows” and“cows.” If it is determined at step 416 that a Webroom already existsfor the topic, at step 418, the applicant is referred to the existingWebroom, for use according to the method 500 illustrated in FIG. 5.

If there is no pre-existing Webroom for a topic, a Webroominfrastructure for the topic is set up at step 418. Infrastructure, forthe purposes of step 418, comprises a defined topic stored in topicdatabase 424, and one or more linked Webroom pages, including anyassociated or embedded applications, stored in Webroom page database 432(or more generally, in a host memory comprising Webroom database 116shown in FIGS. 1 and 2). Web room pages are Web pages having certainfeatures, some of which have already been described, and which will bedescribed in more detail later in the specification, including graphicalobjects and embedded applications for receiving posts of informationfrom users, providing users an option to receive posts, and displayingor otherwise outputting posts to users, providing users an option toindividually rate each post, receiving rating data from users regardingselected posts, and providing users an option to receive rating data invarious formats. Being a species of Web page, Webroom pages may begenerated according to methods known in the art, using a variety ofknown methods to build Web pages having features with thecharacteristics and functionality as disclosed herein. It is anticipatedthat only a limited number of Webroom infrastructure pages, i.e.,template pages, need be developed for this purpose. Such template pagesare essentially empty forms and will be the same or similar for a widevariety of assigned topics, for a given user language and programmingenvironment. The applicable template pages are then copied, assigned aunique address, associated with and modified for the defined topic, andstored in a host memory.

At this point, the Webroom pages are ready to serve as the userinterface for receiving, rating, ranking, linking, storing, andperforming other operations on information, and providing options tousers, according to the methods of the present invention. It should benoted that steps 402 through 418 discussed thus far comprise a processfor, among other things, defining a topic prior to receiving posts ofinformation. It will be evident to one skilled in the art that manyvariations on the described defining process are possible. Whateverparticular process is used, it is preferable to define a unique topicfor each Webroom that has a clear and recognized meaning. Also, it ispreferable to draw upon a general user base to assist with topicdefinition, using an automated or semi-automated process, for thereasons explained above.

At step 420, an initial list of preferred links to related externalsites, called a “toplist,” is generated and stored in database 432 fordisplay on the Webroom pages. Preferably, the content of the toplistwill change during the life of the Webroom, based on new links andrating data provided by the users. Initially, the toplist may be leftempty, but it is preferable to provide an initial list. An initial listmay be provided based on a search for related Web pages using the topicwords as keywords. A search may be performed automatically by submittingthe topic words to one or more search engines known in the art, andselecting a portion of the search results, for example, the toptwenty-five results, on the top list. In addition, it is preferable toprovide the Webroom founder with an opportunity to provide addresses forinclusion in the initial toplist.

Preferably, the founder is also provided with an option to designate anaddress for a Web page of the founder's choice, called a “founder'slink,” for inclusion in the toplist. At step 422, the address isreceived from a founding user and added to the toplist in the mannerdescribed above, thereby providing a link on the Webroom page comprisingthe founder's address. The founder's link preferably receives morefavorable treatment relative to other links on the Webroom page. Forexample, the founder's link may be displayed more prominently than otherlinks, or may be exempted, at least during an initial period, from aranking and review system that is used to remove unused links from atoplist. In this way, a founder may be rewarded for the time and effortinvested in founding a Webroom. At the same time, as a Webroom grows inpopularity and users over time, it is preferable that the founder nolonger be provided more favorable treatment, and be required to competeevenly with other users. A “level playing field” encouragesparticipation from all users and continued addition of new informationto the Webroom. Also, as a Webroom grows in popularity, founder statusbecomes more and more valuable. At some point, the value of founder'slink and other forms of preferential treatment greatly exceeds the valueof the founder's original contribution. This provides an additionalreason and incentive for requiring new contributions of some type tojustify a continuing preferential status.

As a final step in the infrastructure set up process, an initial list oflinks to related Webrooms is generated, similarly to the toplist. TheWeb room topic database 424 is searched according search methods knownin the art, and a list of related Webrooms is identified. A portion ofthe Webrooms are selected, for example, the top twenty-five, forinclusion on the initial list. As with the toplist, the content of theWebroom list is anticipated to change over time, depending on relativeuse and rating information for each related Webroom.

With a defined topic, a toplist, and an initial Webroom list, the newlyestablished Webroom is ready to be opened to the public, in an openingstep 430. Network access for the general user community to the Webroompages is enabled, as is access to the Webroom databases using theWebroom pages. Network traffic is directed to the Webroom pages using avariety of methods known in the art for directing traffic to aparticular page. For example, the Webroom page may be registered withnumerous search engines. Additionally, links, such as banner ads, may beplaced on other popular pages, particularly those dealing with relatedtopics. It is further anticipated that many founders will be interestedin directing traffic to their Webrooms, and will do so by contactingtheir respective communities in various ways. When set-up is completeand users begin linking to the Webroom page, the Webroom preferablyoperates according to the method 500 illustrated in FIGS. 5A and 5B.

It should be appreciated that a Webroom may be established in other waysthan described above, and need not always start with an empty template.For example, an existing chat room or news group may be converted into aWebroom by the addition of Webroom features described above. In suchcase, objects for receiving and responding to posts would already bepresent on the Web page, and would be linked to a database ofpre-existing posts. However, it is anticipated that even if someWebrooms are formed by converting existing, prior art informationexchange groups, it will be necessary to create new Webrooms to meetuser demand for new topics, and to expand the range of topics covered bya Webroom system.

Referring to FIG. 5A, at step 502, the Webroom server receives a requestfor a Webroom home page from a user. The server then initiates a loginprocess 550, shown in more detail in FIG. 5B. At 552, the requestinguser is identified. This may be handled by a login script and password,which is preferred for more secure systems or to accommodate usersaccessing the system other than from the users' usual computer.Alternatively, the user may be identified by reading a cookie or otheridentifying information on the user terminal, or by any otheridentifying method known in the art. After the user is identified, adatabase of user data 406 is checked to determine if the user isauthorized for full system access, at step 554. Preferably, a user isauthorized to view a portion or all of the Webrooms on the system afterregistering only once. Portions of the Webrooms may be restricted oropen to particular users, depending on the identifying information. Forexample, if the identifying information indicates that the user is aminor, access to Webrooms with adult-only content could be restricted.For further example, a particular group of users may set up one or moreprivate Webrooms for access only by members of the group, in which caseaccess to the private Webrooms will be blocked unless the user isidentified as a group member.

If the user is identified as a registered user, user preferences for therequested Webroom are established at 562. In most cases, the user willadopt a set of default preferences to begin with, and will retain theoption of modifying the default preferences for each particular Webroom. User preferences are stored in a database 564 of user preferenceinformation. Further discussion of user preferences is provided later inthe specification in connection with FIGS. 13A, 13B and 13C.

If the user is not identified as already existing in the user database406, at 556, the user is provided with an option to register as a newuser. If the user selects the option, a user profile is established atstep 560. Various amounts of identifying information may be collectedfor the user profiles, depending on the objectives of the system. Ingeneral, it is preferable to balance various considerations, such asease of use, privacy, and accountability, in determining how muchinformation to collect. It is also possible to link a user status withthe amount of information provided; for example, users who providelittle identifying information could be prevented from attaining a highuser status in the system. After the identifying information has beencollected and stored in user database 406, the login process resumes atstep 552, as before.

If the user does not wish to register as a new user, the user isprovided an option to register as a visitor at step 564. If the userdoes not wish to register as a visitor, the user is preferably directedto one or a series of exit Web pages according to the preferences of theWebroom operator. For example, the user may be directed to a Webroomwelcome page that explains the benefits and operation of Webrooms andcontains advertising messages. If the user elects to receive visitorstatus at step 564, then a temporary identification and a set of visitorpreference data are assigned at step 568, typically by reference to adefault database, similarly to step 562. To encourage visitors toregister as users, visitors are preferably prevented from accessing thefull Webroom feature set, and receive a message encouraging them toregister as users when they attempt to use a restricted feature.

After the login process is complete and user or visitor preferences areestablished, at step 504, shown in FIG. 5A, a first Webroom page (a“root menu” page) is displayed at the user terminal. The root menu pagepreferably displays a summary of one or more postings in the Webroomdatabase, a list (or a link to a list) of toplinks, and a list (or alink to a list) of related Webrooms. Additionally, the root menu pagepreferably has a menu providing users with various Webroom options, forexample, options for setting user preferences, and may include one ormore advertising messages. Various options are diagrammed as steps 506,508, and 510 in FIG. 5A. It should be noted that, although the foregoingsteps are diagrammed as sequential steps, one skilled in the art willrecognize that the steps may be selected in any sequence from the rootmenu.

A substantial portion of the root menu page is preferably used fordisplaying a sequence of user posts. A “post” typically comprises a textmessage composed or provided by a user, but may include or comprise anaudio file (such as a recording of the user speaking), graphical files,such as video or still photographs in various file formats, applicationfiles, such as content files for use with word processing andspreadsheet applications, and other forms of user content files.However, depending on the bandwidth, processing and memory constraintsimposed by the Webroom server, it is preferable to limit the file sizeof user posts, and/or to require that posts be submitted in one or moredesignated file formats, e.g., as text files. The summary of postsdisplayed on the root menu page preferably displays summary informationabout each post, such as the contributing user identification, date andtime submitted, subject line information, and length of the posting.

Textual posts are preferably displayed in their entirety, or in summary,depending on whether or the display is organized chronologically (i.e.,is unthreaded) or as threaded on subject threads. Chronological postingsare preferably displayed in their entirety, to permit rapid scanning ofall material submitted within a given time frame. Threaded postings arepreferably displayed in summary, so that more of the subject threads canbe viewed on a single screen. Depending on user preferences, variousother combinations of summarized or entire posts may be displayed.

Additionally, the root menu page preferably provides for display of theposts, or summary of posts, in various orders and groupings, as shown inFIGS. 5C and 5D. Webroom page 570 is preferably comprised of one or moreframes 571 and 573. Posts 585, comprising subjects 580 and messages 582,are summarized in a format showing various summary objects such as apost ID number 574, the contributing user 576, post date 578, post time579, subject 580, and an initial portion of the message 582, for eachpost. In FIG. 5C, the posts 585 are grouped and ordered according totheir position on a subject thread 572. For example, post No. 290, byuser “MaryM,” is in response to post No. 273, by user “DrJones,”regarding the subject of measles. Post No. 296, by DrJones, is inresponse to the post by MaryM, and post No. 304 is in response to theinitial post by DrJones. Thread 572 displays the relationship of postsand responses giving rise to the subject thread. The summary of posts585 may preferably be scrolled using a familiar interface device, forexample arrow keys on a keyboard, a computer mouse, and/or a graphicaldevice such as scroll bar 584. One skilled in the art will recognizethat a wide variety of formats for displaying posts grouped according toa subject thread are possible, wherein each format groups posts andtheir associated responses in order of response.

Page 570 preferably includes a toggle object 586, for providing users anoption of selecting a variety of formats for displaying the posts 585.Object 586 is preferably a graphical object, such as a button or radiobox, that can be selected and activated by “pointing and clicking” usinga pointing device, such as a computer mouse. Object 586 may be locatedin the same frame 571 as posts 585, or it may be located in a separateframe 573, which preferably contains other command menus and commandobjects, such as objects 590, 591, and 592.

By activating toggle object 586, a user can toggle between two or moreformats for displaying posts 585. For example, a user may select to viewposts 585 in reverse chronological order of submission, as shown in FIG.5D. In this view, frame 571 contains a summary of the Webroom posts,beginning with the most recently submitted posts and proceeding to theoldest posts. The post summary objects are preferably the same, orsimilar to the summary objects as displayed in threaded format. However,the unthreaded (i.e., not grouped according to a subject thread) formatpreferably includes one or more rating icons 588 and subject icons 593associated with each post. The rating icons 588 preferably indicaterating information pertaining to each post. For example, rating icon 588might reveal five stars for the most highly rated posts, with a lessernumber of stars for lower rated posts; one or more iconic candle flamesindicating the degree to which users have rated the post to be a flame;and one or more orange blobs indicating the degree to which users haverated the post to be spam. In the alternative, rating icon 588 mightreveal a numeric score for various rating categories.

Subject icon 593 may be provided to indicate a particular subject threadthat pertains to the post. For example, all posts relating to aparticular thread may be coded with a particular color. In thealternative, each post background is preferably provided with a coloredbackground 589, color coded to relate to a particular subject thread.Color coding permits a user to view all postings in chronological orderas they are submitted (or other order), while retaining subject threadinformation for each post. It should be noted that a wide variety offormats for coding rating information and subject threads for a list ofpostings may be used within the scope of the present invention.Additionally, posts may be summarized in a variety of orders, forexample, according to a rank determined by post rating data, or as acombined function of date and time submitted and a post rank based onuser-provided data.

Page 570 is preferably provided with a related Webrooms button 590. Uponactuation, button 590 displays other Webrooms which are deemed to berelated to the currently viewed Webroom. In preferred embodiments, userswho have passwords and can post in the Webroom are eligible to nominateand vote on whether a Webroom is related to another Webroom. Users whobelieve that one Webroom should have a link from another Webroom (andthus be related) can nominate the Webrooms to be related via a nominatedWebroom button 591. In one embodiment, nominated related Webrooms bothappear on a list that exists on each respective site (thus, site Aappears on the list of nominated related Webrooms on site B, and viceversa). Members of both Webrooms then have the opportunity to review theother Webroom and determine if that Webroom should appear on the list ofrelated Webrooms, by rating the Website accordingly. The ratings fromboth Webrooms are then aggregated, and, once a minimum amount of ratingdata is received, a determination is made as to whether the rooms willbe listed on the “related Webroom” list or link, as discussed later inthe specification. If a Webroom (A) is found to be related to anotherWebroom (B), both Webrooms may appear on a list of related Web roomswhen a user views one or the other Webroom, depending on various factorssuch as the amount of traffic the Webroom receives and the number oflinks already listed on the Webroom related links list. For example, ifWebrooms (A) and (B) are related, and (A) relates to a general topicreceiving a large amount of traffic, while (B) relates to a narrowlydefined topic with relatively little traffic, then a link to Webroom (A)may appear on Webroom (B), while Webroom (A) does not contain a link to(B). In the alternative, if Webroom (A) has relatively few links (whichmay occur, for example, when it is relatively new), then the link to (B)may appear on the (A) list until the (A) list contains a predeterminednumber of links.

Page 570 preferably includes a toplink button or menu object 592 forpresenting links to related Web pages (that are not Webrooms), similarto the process described for Webrooms in connection with Webroom button590. The process of linking to, and rating links to, related Web pages(and Webrooms) is described in more detail later in the specification.Additionally, a button (not shown) for nominating related Web pages,similar to button 591 for Webrooms, may be provided. In general, itshould be understood that Webroom page 570 is not limited to display ofthe objects discussed in connection with FIGS. 5C and 5D, and maycontain various other objects, such as advertising messages, helpbuttons, search objects, text objects, and graphical objects of variouskinds. Additionally, the arrangement of the objects is not limited tothe arrangement described, and one skilled in the art will recognizethat various other arrangements of the above elements will be within thescope of the invention.

Referring again to FIG. 5A, at step 506, users are provided an option toreceive posts. If a user selects the option, a post display step 602 isinitiated, as shown in FIG. 6A, for displaying the full posting at theuser's terminal. Preferably, every post summary format provides eachpost with at least one object that may be selected to view the entirepost, preferably in a new window or frame. It should be noted that“display” is used in a general sense. For example, if the post comprisesan audio or video file, the audio or video file will be played at theusers terminal, along with a display of any supplemental information.Additionally, users may be provided with an option to receive textmessages in an audible format by incorporating a text-to-speech engine,of which several are known in the art, as part of the Webroomapplication package. Posts may be displayed in numerous ways familiar tothose skilled in the art, for example, using a distributable applicationwindow that is continually updated as new posts are added to the Webroomdatabase.

At step 604, users are provided an option to individually rate each postviewed.

An exemplary Web page showing features for providing users this optionis shown in FIG. 6B. Webroom post page 650 contains a display of atleast one post 676. Adjacent to each post 676, a respond button 658 andone or more voting objects 660 are displayed. Webroom page 650additionally includes a subject line 652, a general post button 654, ascrolling object 656, and a tolerance bar 670, which is discussed inmore detail later in the specification in connection with FIGS. 13A and13B. Users may scroll through the postings by using scroll objects 656,may post a response to any particular posting using a respond button654, and may submit a general posting (not in response to any particularposting) using post button 654. Score display bar 672 provides users anoption to receive rating data. Scores may be displayed directly on bar672, which preferably is programmed to provide additional rating datawhen selected by a user, for example, when double-clicked on.

Vote objects 660 provide users an option to rate posts according to atleast one predetermined criteria. Several different rating criteria(also called categories), for example, spam, flame, and relevance arepreferably used. Various formats of vote objects may be provided. Forexample, a voting bar comprised of a decrease button 664, a score field666, and an increase button 668 may be provided. In this case, a usercan rate each post by increasing or decreasing the score in the scorefield using the increase button 668 and the decrease button 664, or byentering a score directly in score field 666. Voting objects may betailored for the intended Webroom user community, for example, moresophisticated voting objects and rating schemes may be presented in anacademically-oriented Webroom, as opposed to a Webroom for youngchildren.

Whatever specific rating scheme is used, the scheme is preferablydesigned to be fun and easy to use, while at the same time collectinginformation about each post that is as accurate and complete as requiredto reliably reflect the information value of posts with respect to eachdesignated Webroom topic. To accommodate scoring and ranking of posts,it is preferable for at least a portion of rating data received fromusers to comprise a quantitative rating. For example, a numeric rankingof relevance between zero and ten, with ten indicating the highestpossible relevance, and zero indicating no relevance whatsoever, is anexample of a quantitative rating. Additionally, an alphabetic ratingsystem, such as grading from “A” to “F,” is also a quantitative ratingsystem, because each letter grade can be readily assigned a numericvalue. In addition to spam, flame, and relevance categories, scoringcategories may include credibility, accuracy, clarity, wit, or anycategory of interest to the user community. An overly complex scoringsystem will tend to discourage use, so the scoring system should belimited to scoring categories of interest to each particular Webroomuser community. It is anticipated that the categories of spam, flame,and relevance will be of interest to most Webroom users. Furthermore, atleast one relevance category is needed for developing a relevancescoring and ranking system that promotes topical organization andself-evolution as described above.

In order to prevent misuse of the rating system, it is preferable tolimit the number of times a user may rate any particular post.Preferably, each user may only rate each post a maximum of once, and nouser may rate his or her own posts. Additional limitations may be placedon rating. For example, each user may be limited to a predeterminednumber of votes per Webroom within a given time period. Such limits maybe based on a user ranking, for example, users identified as providingonly spam could be prevented from rating any posts, and highly rankedusers could be rewarded with additional rating privileges. Basing ratingrights on user status has the advantage of providing more control overthe Webroom content to the most interested and knowledgeable users, thusfacilitating growth and organization of higher-quality information.

Each post 676 in Webroom page 650 preferably includes a private e-mailbutton 674. E-mail button 674 provides a convenient way for users tosend e-mail directly to authors of posts, without requiring the authorsto make their e-mail address public. Using the private e-mail button 674and associated method, communication between members of the forum isenabled, while “harvesting” of e-mails by others (such as would-be“spammers”) is prevented. Preferably, the only way to contact the memberusing the Webroom page 650 is by selecting the e-mail button 674 fromwithin a post authored by the intended recipient, thus preventing massmailings such as are typically used for unwanted commercialsolicitations. When a user selects e-mail button 674, an e-mail messageauthoring window (not shown) as known in the art is provided to theuser. After completing the message to the selected author, the usersends the message to the Webroom server. The server then forwards themessage to the post author by referencing a database of private e-mailaddresses provided by the forum members.

Referring again to FIG. 6A, if a user elects to provide rating data fora particular post at step 604, then the rating data provided by the useris recorded in post rating database 608, and indirectly inuser-associated rating database 610. Before recording the data in userdatabase 610, the rating data is preferably processed according to aprocess illustrated in more detail by FIG. 6C. The process 620 shown inFIG. 6C may be initiated at any time, that is, it may be performedsynchronously or asynchronously with the posting process. Process 620 ispreferably repeated continuously to process new rating data as it isadded to the system. Process 620 preferable executes in the systembackground without interrupting user actions, such as searching,receiving, or rating posts. It should be noted that steps 624-632 ofprocess 620 all require access to post rating database 608. The detailsof process 620 will vary depending on variations in the desired outputand the data structure used for post rating data.

An exemplary data structure for post rating data is illustrated in FIG.6D. Data structure 680 is preferably realized in a relational databaseorganized according to a database standard, for example SQL. Any numberof user levels 682 are present, with each user level having any numberof rows 686 and columns 688. It should be noted that the terms “level,”“row,” and “column” represent dimensions that are not topographicallydistinct in the context of a relational database. A data structureaccording to the present invention is, of course, not a physicalstructure, and may have any number of dimensions. The illustration ofthree dimensions in FIG. 6D is for simplicity of explanation. In theexample illustrated, each row 686 represents rating data for aparticular posting, for example, post 1, post 2, etc. Each column 688represents rating data in a particular category, for example, category1, category 2, etc. Each level 682 represents rating data contributed bya particular user, for example, user 1, user 2, etc. Level 684represents an aggregate of rating data from multiple users. An aggregateis any statistical measure that reflects the overall value of a set ofquantitative ratings, such as a sum, a weighted average, a simpleaverage, a rolling average, a median value, or similar measure. Eachcell, for example, cell 690, is defined by a row-column intersection ona particular layer. Each layer contains corresponding cells, asindicated by the dashed vertical lines 692. For example, cell 685 oflevel 684 contains an average of rating data contained in the cellsdefined by the intersection of row 1, column 1, on all user levels 682,and indicates a simple average of the user ratings for post 1, category1.

One skilled in the art will recognize that a wide variety of aggregatestatistical data may be developed across and within levels of the datastructure for use in the process 620. Referring again to FIG. 6C, atstep 622, the post rating data is read from post rating database 608 tobegin the process.

In an alternative embodiment, to account for variability between users'rating tendencies (for example, some users will tend to assign scoresthat are consistently higher or lower, on an aggregate basis, than otherusers in any given category), a step 624 of computing a relativeweighting factor for each user is performed, to be applied to the userdata provided by that user. For example, user weighting data for eachuser may be developed by aggregating columns on each user level 682shown in FIG. 6D. To reduce system load, user weighting factors may becomputed less often than post rating and scoring data; for example, step624 may be performed periodically, such as once per day, and duringoff-peak hours. At step 626, the computed user weighting factors areapplied to the user rating data, for example, by performing a matrixmultiplication or other transformation operation on the rating data, toobtain weighted rating data. At step 628, the weighted data ratings areaggregated for each category of rating and each posting to obtain a postscore in each category, which is recorded in the rating database 608 atstep 630. One skilled in the art will recognize a variety of otherweighting schemes designed to correct for variability among ratingagents, which may be usefully employed to operate on user data withinthe scope of the present invention. One skilled in the art will furtherrecognize that steps 624 and 626 may be omitted entirely, to providesingle-vote-per-user, single-unit-per-vote rating, which provides theadvantages of simplicity and ease of implementation.

The post scores are used to compute and record a post rank at step 632.A post rank measures the posts' relative scores with respect to otherposts in the Webroom. It is anticipated that as the number of posts in aWebroom grows, a higher score will be required to maintain a givenranking. Additionally, it is preferable to time-stamp rating data anddiscount older data in the ranking scheme. Thus, older posts mustcontinue to be viewed and rated in order to maintain their rankingrelative to newer posts. Posts that fail to achieve pre-establishedminimum rankings, i.e., a “community standard” for posts, may be removedfrom the Webroom. Community standards for posts may be established bydefault at the time of Webroom founding, and may be modified as desiredby users or a system administrator. However, setting standards too highwill tend to cause posts of interest to some users to becomeunavailable. Thus, it is preferable that standards for posts be keptrelatively low. Users not wishing to view lower-ranked posts may filterthem out using a user preference process as described elsewhere in thespecification.

As previously discussed, maintaining an accurate ranking for posts canprovide an important impetus for evolution towards more highly organizedWebroom systems, by organizing the best information closest to eachidentified topic. Both post ranks and post scores may be associated witheach post, and made available to users by a variety of selectionmethods. For example, one method enables searching posts by keyword andrank (or score), so a user could search for, for further example, theposts containing the word “Jersey cows,” having a relevance scoregreater than five and a spam score less than two. By searching amonghigher-ranked posts only, i.e., by setting user preferences to filterout lower-ranked posts, a user may selectively reject posts that do notmeet the user's threshold criteria. Another method is to display postsaccording to rank within a Webroom, as discussed above. However,displaying posts in a ranked order, or omitting lower-ranked posts froma display, has the disadvantage of disrupting the chronological orthreaded display schemes described above. Disruptive effects may bereduced by using a placeholder, which indicates the presence of anomitted item, as previously described. In the alternative, the rankedpost ordering is presented in an alternative display that may beselected by activating a user command, such as a toggle button. Stillanother method, which avoids the disadvantage of disruptingchronological or threaded displays, is to display scores adjacent toeach posting, as done with the score display bar 672 discussedpreviously.

At step 634, each post for which a score has been newly computed duringprocess 620 has its new score recorded in a database 610 ofuser-associated rating data. A data structure similar to data structure680 may be used for user-associated rating data, in that a level foreach user may be defined, having columns corresponding to categories,and rows corresponding to posts. The principal difference resides in thecell content. In the user-associated rating data structure, each cellcontains an aggregate score of the posts contributed by the particularuser, instead of a userprovided rating of another user's post, aspreviously described. In other words, rating data is associated witheach contributing user. For example, a record for a user who hadcontributed three posts would contain the rated post scores for theuser's three posts, as developed from rating data contributed by otherusers. Each score is recorded in a record for the contributing user,preferably superseding any prior aggregate scores recorded for the samepost and user. The user rating scores may be aggregated in a similarmanner to post rating data, for developing a user score. The users maybe ranked like posts, based on relative scores, principally forproviding an incentive to users to contribute high-quality posts. Asindicated at step 636, process 620 may be repeated for each unscoredpost until finished.

Having thus described a process for receiving rating data pertaining toselected posts, the description of user interaction with Webroom postsis continued. Returning to FIG. 6A, if the user does not elect toprovide rating data at step 604, the user is provided an option to posta response at step 612. If the user elects to post a response, forexample, by activating a response object 658, then at step 614, theresponse is received and recorded in database 616 containing post data.It is preferable to automatically refresh the user's Web room page afterstoring the post, so the user may view it on Webroom page 650. If theuser does not elect to post a response, and after completing a response,the user is provided the option of continuing to receive and reviewposts at step 618. If the user elects to continue, the process may berepeated any number of times, beginning with step 602. If the user isfinished viewing the postings, the user is returned to the root menupage 570.

Returning to FIG. 5A, a second option on the root menu page 570comprises an option 508 to select and rate links to related Web pagesfrom a list of Web pages (toplist) provided on the root menu page 570.Selecting a link to a related web page initiates a process 700 forviewing and rating related Web pages. Related Web pages add an importantcomponent to the topical information presented by each Webroom.Furthermore, links to a Webroom page on related Web pages provide forincreased traffic to the Webroom that compensates for the links to therelated Web pages provided by the Webroom. Thus, the toplinks providefor a mutually beneficial and cooperative relationship between Webroompages and other information resources on the network. In general,tracking incoming traffic from a related page, or a potentially relatedpage, is important for creating and maintaining toplists, becausetraffic exchange and cross-promotion is central to this mutuallybeneficial relationship.

Process 700 begins at step 702, when the requested related Web page isdelivered to and reviewed by the user. In an embodiment of theinvention, if the related Web page is not reached using an existing linkon a toplist, the address of the page is noted in a Webroom database,and a count of incoming traffic from the page is initiated. In analternative embodiment, page requests for potentially related pages arealso counted. Additionally, users may be provided with an option tonominate other Web pages for inclusion in the toplist, similarly causingthe address of the page to be stored and page requests to be tracked.Pages receiving a sufficiently high number of requests may be promotedto the toplist, and conversely, pages with too little activity may beremoved from the toplist.

At step 704, the user is provided an option to rate the Web page.Preferably, the related Web page is presented in a frame of the Webroompage, so that the option to rate the related Web can readily be providedin an adjacent frame of the Web room page. In the alternative, the usermay elect to rate a related Web page by selecting a link on the toplistin conjunction with a “vote” or “rate” command selected using a menu orother selectable object.

At step 706, the page rating data from the reviewing user is receivedand stored in a database 708 of page rating data. If the Web page isprovided by a Webroom user, for example, a founder, the rating data isalso stored in the database of user-associated rating data 610,similarly to the process described above with respect to post ratingdata. In many respects, rating a Web page is similar to rating a userpost, the principal difference (for rating purposes) being that relatedWeb pages may contain links back to the Webroom page. Also, different oradditional rating categories may be appropriate, for example, thecriteria of “spam” and “flame” are less appropriate for a Web page,whereas other categories, such as response time or page organization,may be of more interest to users. Of particular importance to rating Webpages are traffic data, such as the number of times the Webroom page isrequested from the related Web page (incoming traffic), and the numberof times a page is requested from a Webroom page (outgoing traffic). Inparticular, users who create related Web pages that refer a relativelylarge amount of traffic to the Webroom are preferably recognized andrewarded (for example, by designating the related Web page as a toplink)based on comparative ranking of traffic data. Furthermore, the higherthe number of page requests, the more likely it is that the related pagecontains relevant or useful information, thus making outgoing trafficworthy of consideration also. However, at present, implementation ofoutgoing traffic tracking requires a more involved technical scheme thantracking incoming traffic, and is therefore omitted in some embodiments.One skilled in the art will recognize that the process 620 for receivingand analyzing rating data for posts may be adapted for related Web pagesrating data without great difficulty. Further details concerning ratingrelated Web pages, and using rating data, are provided below inconnection with FIGS. 11A-C.

At step 712, the user is presented with an option to receive anotherrelated Web page. If the user selects the option, process 700 isrepeated, beginning at step 702. If the user declines to receive anotherpage, the user is returned to the root menu page 570, as exemplified byprocess 500 of FIG. 5A. A third option on the root menu page 570comprises an option 510 to select and rate links to related Webroompages from a list of Webroom pages provided on the root menu page 570.Selecting a link to a related Webroom page initiates a process 800 forviewing and rating related Webroom pages. Providing links to relatedWebroom pages is one of the essential features for providing a system ofrelated topically organized, self-evolving information exchange groups,as discussed above. To promote a high level of organization, links tothe most closely related Webroom pages are continually established andmaintained, and links to Webroom pages that are not as closely relatedare continually deleted. Similarly to related Web pages, user rating anduse” data, as received from a process such as process 800, is theprimary basis for the establishment and maintenance of links to relatedWebrooms.

Process 800 begins at step 802, when the requested related Webroom pageis delivered to and reviewed by the user. If the related Webroom page isnot reached using an existing link on the referring Webroom page, thetopical cross link is preferably noted in a Webroom database and a countof cross link use is initiated. This may be accomplished using anominating button as described previously, or otherwise providing usersan option to link to Webroom pages that are not on a current list oflinks, for example, through a Webroom search process. Webroom pagesreceiving a sufficiently high number of requests are promoted to a liston the referring page, and conversely, cross links with too littleactivity are removed from the referring page. At step 804, the user isprovided an option to rate the Webroom page, which may be accomplishedas discussed above with respect to rating related Web pages.

At step 806, the Webroom rating data from the user is received andstored in a database 808 of page rating data. In virtually all respects,rating a Webroom page is similar to rating a related Web page, theprincipal difference (for rating purposes) being that different oradditional rating categories may be appropriate for related Webroompages. For example, the criteria of response time or page organizationare less appropriate for Webrooms, which are typically delivered fromthe same or related servers as the referring Webroom, and are organizedin a standardized fashion. One skilled in the art will recognize that,similarly to related Web pages, the process 620 for receiving andanalyzing rating data for posts may be adapted for Webroom data withoutgreat difficulty. Further details concerning rating Webrooms, and usingrating data, are provided below in connection with FIGS. 12A-C.

At step 810, the user is presented with an option to continue viewingthe related Webroom page (which is likely to contain a link back to thereferring Webroom). If the user elects to continue viewing the Webroom,at step 812, a process 500 of root menu operation, as illustrated inFIG. 5A, is initiated. However, if the user is already registered, loginprocess 550 is preferably abbreviated by automatically registering theuser in the new Webroom, and accepting the original login (unless aspecial security consideration applies to the new Webroom). If the userdecides to return to the referring Webroom, the user is returned to theroot menu page 570, as exemplified by process 500 of FIG. 5A. Thus, auser may preferably freely surf between Webrooms, as if perusingdifferent topics within a single Webroom. In effect, a system organizedin this manner operates as if it were a single Webroom with multipletopics.

Returning to FIG. 5A, the root menu contains an exit option 512, whichmay be exercised by linking to another site, or by inactivity for aproscribed period of time. However, the root menu is preferably alwaysavailable, and the chief consequence of exiting is triggering arequirement to repeat the login process 550 when access to the Webroomis again desired by the user.

Periodically, maintenance process 900 is preferably performed, asillustrated in FIG. 9. Regular performance of process 900 on eachWebroom of a system of Webrooms operated and used as described abovewill result in self-evolution of the system to a higher level of topicalorganization. Process 900 is preferably executed as a backgroundoperation. Like maintenance procedures generally, it is preferable toexecute process 900 when the demand on system resources is otherwiselow, as during off-peak hours. At step 902, the process is initiated bya timer or other system parameter set to indicate an appropriate timefor performing the process 900. Initially, the subroutines 1000, 1100,and 1200, diagrammed in more detail in FIGS. 10A, 11A, and 12A,respectively, are run in sequence.

Referring to FIG. 10A, subroutine 1000 comprises a process for rankingusers. As previously described in connection with step 634 of process620, each Webroom preferably has a database of user associated ratingdata 610. Database 610 preferably comprises an aggregate score for eachpost contributed by the user. At step 1002, rating information isobtained from database 610. At step 1004, each user's aggregate scorefor each category is computed. For example, if in any given ratingcategory, such as relevance, the user's ten posts had each been ratedten times, an aggregate value, such as an average, would be computed forthe one-hundred ratings (also called votes) received. Other statisticalmeasures, such as a median value and a standard deviation, may also becomputed at step 1004. A rolling average may be useful for trackingchanges in the user's performance over time. One skilled in the art willrecognize that various other statistical measures may be computed,depending on the parameter to be measured. For example, statisticalmeasures may be employed to detect aberrations in rating data that mayindicate misuse of the voting process, or other data errors. For thepurpose of promoting topical organization, aggregate scores that fairlyreflect the value of ratings received by each user, and user activity,are preferred. Thus, it is preferable to identify and disregard aberrantdata using statistical tools as known in the art.

At step 1006, the users are preferably ranked according to their scoresin each category and according to their activity (for example, thenumber of posts contributed). Preferably, an overall ranking isdetermined. Additionally, a ranking in one or more rating or activitycategories may be determined. For example, users may be separatelyranked according to their scores in a relevance category, or accordingto the number of posts contributed. Ranking may be continuous, forexample, in a group of one-hundred users, assigning everyone a uniquenumber between one and one-hundred; or discrete, grouping closely-rankedusers into discrete ranking levels; or any combination of discrete andcontinuous ranking may be used. Also, rating and activity informationmay be combined across categories to classify users into different typesand levels. Whatever ranking system is used, it should be designed tofacilitate the central purpose of motivating users to providehigh-quality information. Thus, desirable behavior should be recognizedwith high ratings, and undesirable behavior with low ratings.Preferably, users with favorable ratings are rewarded with privileges,such as additional or enhanced voting privileges, the right to designateone or more toplinks of their choice, public recognition on Webroompages, and other rights or recognition tending to increase desirableusers' influence on Webroom content and traffic direction. Incentivessuch as prizes of merchandise or cash may also be awarded, if desired.Conversely, extremely negative scores (such as high spam scores) shouldbe discouraged by imposing restrictions on access and use of theWebroom.

At step 1008, the user ranking and scores are recorded in database 610.A table 1020 exemplary of ranking and scoring data that may be recordedis provided in FIG. 10B. Table 1020 comprises rows 1022 and columns1024. Each row of rows 1022, for example, rows 1031-1034, is assigned toa unique user. Each column, for example, columns 1041-1050, is assignedto a rating or activity category. It should be noted that table 1020contains a section of columns (e.g., columns 1041-1050) for datapertaining to a particular first Webroom, and another section of columns(not shown) for general user data, such as the user name and e-mailaddress. A different table 1020 containing unique rating data may begenerated for different Webrooms, reflecting that a user is rateddifferently in different Webrooms. Exemplary data is provided in eachcell of the table 1020 to illustrate how different rating and activityinformation may be used to classify users.

For example, column 1041 contains a count of the posts contributed byeach user, and column 1042 contains the average post length in words.Columns 1043 through 1046 contain each user's aggregate score in therespective categories of flame, spam, relevance, and accuracy. Column1047 contains a count of the number of votes received, that is, thenumber of times the user's posts have been rated by other users. Column1048 contains a count of the number of times each user has requestedposts from the server. Column 1049 contains the number of linked Webpages relating to the Webroom topic that each user has provided. Column1050 contains a classification, or rank, assigned to each user on thebasis of other information in the table. A comparison of the users ismade using the exemplary data. Row 1031 pertains to USER1, showingrelatively moderate levels of activity and ratings as compared to theother users. Accordingly, USER1 is assigned a status of “Active Member.”Data for USER2 is shown on row 1032. USER2 has relatively few lengthierposts, which are highly rated for accuracy and relevance, and which havereceived a proportionally high number of votes. USER2 also has fiftylinked Web pages. Thus, USER2 is assigned a status of “Expert.” Incontrast, data for USER3 in row 1033 clearly indicates a large number ofspam postings with no rated relevance, so USER3 is assigned a status of“Spammer.” Such a status preferably will result on restrictions onUSER3, for example, USER3 may be prevented from submitting or ratingposts. Data for USER4, in row 1034, indicates post viewing activity withno contribution of posts, so USER4 is assigned a status of “Lurker.” Oneskilled in the art will recognize from the foregoing example that a widevariety of rating and activity data may be recorded, and used toclassify and rank users in numerous ways, without departing from thescope of the invention.

Preferably, selected user ranking information may be viewed by Webroomusers.

For example, a user directory page 1060 may be provided, as illustratedin FIG. 10C, preferably accessed from a link on root menu page 570. Userdirectory 1060 is preferably available in a variety of formats, forexample, in alphabetical order, or according to user classification orrank in various rating categories, which may be selected using formatbutton 1062. In FIG. 10C, a format showing users classified in discretelevels is shown. Each user is represented by an object 1064 on directory1062. Each object 1064 preferably comprises a hyperlink. Preferably, byselecting any object 1064, a user may access a detailed user informationpage 1070. Information page 1070 contains the user name 1072 and userstatus 1074. Additional information may include a graph 1076 or otherpresentation of user activity and rating information, specific activityinformation, such as last date of use 1078 and average use level 1080.Users are preferably provided an option to submit information 1082 of abiographical nature for display on information page 1070. Page 1070 ispreferably provided with a directory button 1084 for accessing the userdirectory page 1060.

The presence of user rating data lends itself to various possibilities.In one embodiment of the instant invention, the Webrooms contain asetting allowing members to be exiled based, in part, upon their userrating information. That is, in the event that a user's rating fallsbelow certain pre-established “community standards” for users, theuser's access and use rights to the Webroom are restricted, up to andincluding termination of all access rights. Community standards areestablished by a founding user, or in the alternative, determined by allusers, or a selected portion of the users, such as higher-ranking users.In another alternative embodiment, no community standards are set, buteach user sets personal standards using preference information asdiscussed below in connection with FIGS. 13A and 13B. Using personalpreference information, members may in effect be exiled by individualusers, for those users only, such that no posts made by the exiledmember will be displayed to the self-selected users. It should beunderstood that members can be exiled, or have their rights partiallyrestricted, from individual Webrooms or across groups of Webrooms (orgroups of related Webrooms) or from all Webrooms, depending on systemsettings. In the usual case, however, users are rated, ranked, and ifnecessary, restricted with respect to particular Webrooms only.

In addition to process 1000 for ranking users, maintenance process 900preferably includes a process 1100 for ranking toplinks, illustrated inFIG. 11A. As previously described in connection with step 706 of process700, each Webroom preferably has a database of related Web page ratingdata 708. Database 708 preferably comprises rating and activityinformation for each linked Web page, and for Web pages that are not onthe toplist but are otherwise identified as prospective Webrooms forplacing there. At step 1102, rating and activity information is obtainedfrom database 708. At step 1104, an aggregate score is computed for eachrating and activity category. As discussed in connection with process1000, aggregate scores may be derived using a variety of differentstatistical measures.

At step 1106, the Web pages are assigned a score in each rating andactivity category. At steps 1108 and 1114, Web pages that fail toachieve a predetermined minimum score in one or more categories areidentified and their links are removed from the toplist. Also at steps1108 and 1114, Web pages that have newly achieved a predeterminedminimum score are added to the toplist. At step 1110, the links in thetoplist are ranked. Preferably, an overall (or default) ranking isdetermined for the toplist. Additionally, a ranking in one or morerating or activity categories may be determined for providing users anoption to view alternative rankings. For example, Web pages may beseparately ranked according to their scores in a relevance category, oraccording to the number of times the page is linked to from the Webroom,i.e., according to their popularity. Ranking is preferably continuous,that is, toplinks are preferably ranked in a sequence. Whatever rankingsystem is used, it should be designed to promote a central purpose ofidentifying the best incoming traffic generators, and the most closelyrelated and useful Websites. Pages that fail to meet minimum standards,which may vary depending on the quality of other pages on the toplist,are removed from the toplist.

Pages that are removed from the toplist may be retained on a list ofnominated related pages, according to an embodiment of the invention.Pages on a nominated list may be similarly scored and ranked as pages onthe toplist. Pages on a nominated list that achieve a sufficiently highscore may be promoted to the toplist. Pages with a score below a minimumstandard for the nominated list may be periodically removed from thenominated list. One skilled in the art will recognize that, although twolevels of lists (a toplist and a nominated list) have been described,any number of levels of lists may be implemented according to themethods of the present invention. Furthermore, separate lists may bemaintained in different categories, for example, “best referenceinformation,” “humorous links,” and so forth.

At step 1112, the page rank and scores are recorded in database 708. Atable 1120 exemplary of ranking and scoring data that may be recorded isprovided in FIG. 11B. Table 1120 comprises rows 1122 and columns 1124.Each row of rows 1122, for example, rows 1131-1132, is assigned to aunique page. Each column, for example, columns 1141-1151, is assigned toa rating or activity category. It should be noted that table 1120contains a section of columns (e.g., columns 1141-1149) for datapertaining to a particular first Webroom, and another section of columns(e.g., column 1150) for general page data, such as the user associatedwith the page, page size, and so forth. Each Webroom has its own table1120 containing data unique to the Webroom, reflecting that pages arerated differently with respect to different Webrooms. Exemplary data isprovided in each cell of the table 1120 to illustrate how differentrating and activity information may be used to classify pages.

For example, column 1141 contains a count of the number of times theWebroom has been accessed from a link (if present) on the related Webpage, and column 1142 contains a count of the number of votes received,that is, the number of times the page has been rated by users. Columns1143 through 1147 contain each page's aggregate score in the respectivecategories of relevance, accuracy, ease of use, server responsiveness,and fun. Column 1148 contains a classification assigned to each page onthe basis of other information in the table. Column 1149 contains thepage rank relative to other pages in the same classification. Column1150 contains the identity of a Webroom user who owns the page, if thereis any such user for the page. A comparison of the pages is made usingthe exemplary data. Row 1131 pertains to PAGE1, showing relativelymoderate levels of activity, high relevance, accuracy, ease of use, andresponsiveness ratings, and a relatively low fun rating as compared tothe other pages. Accordingly, PAGE1 is assigned a status of “ExpertPage.” Data for PAGE2 is shown on row 1132. PAGE2 has a relatively highlevel of activity, and good relevance, ease of use, and responsivenessscores, while not being rated for accuracy. PAGE2 also has a relativelyhigh fun rating. Thus, PAGE2 is assigned a status of “Fun Page.” Oneskilled in the art will recognize from the foregoing example that a widevariety of rating and activity data may be recorded, and used toclassify and rank pages in numerous ways, without departing from thescope of the invention.

Preferably, selected toplink ranking information may be viewed byWebroom users. For example, toplink menu 1160 is preferably provided onroot menu page 570, as illustrated in FIG. 11C. Menu 1160 preferablycontains a list 1164 of toplinks in a ranked order. Each toplink in thelist comprises a hyperlink 1161 to its related Web page (or Web site),and is preferably provided with a hyperlink 1162 to a toplinkinformation page 1170. Each toplink may additionally be provided with away to vote on the linked Web site, such as a vote button (not shown)similar to those used for voting on posts. Information page 1170 ispreferably provided with graph 1174 or other presentation of pageactivity and rating information, specific activity information, such aslast revision date 1175 and average use level 1176. A brief summary 1178of page content is also provided. Additionally, page 1170 preferablyincludes a hyperlink 1180 to a Web map page 1181. A Web map is a pagefor mapping a Web page or web site, as described in the co-pending U.S.patent application, Ser. No. 09/549,505, “METHOD AND SYSTEM FOR MAPPINGA SITE ON A WIDE AREA NETWORK,” filed Apr. 14, 2000, which applicationis specifically incorporated herein, in its entirety, by reference.Toplink menu 1160 additionally includes more button 1166 for scrollingforward through the toplink list, and a back button 1169 on applicabledisplays 1168 of the toplist, for scrolling backwards. In an embodimentof the invention, a different toplink menu 1160 is provided fordifferent, categorized lists of links; for example, a list of “expert”links and a list of “fun” links. Additionally, lists of nominated linksare preferably provided in a format similar to the toplink menu 1160.

Lists of links, such as toplist 1160, may be displayed in a variety ofways, but are preferably accessible through a pull-down or pop-up menuon a home frame of the Web room page. This format of display removes thelists from the display when they are not wanted, while at the same timeallowing for ready viewing and accessing of the links. One skilled inthe art will recognize that the functions described above may beimplemented in a wide variety of graphical formats, without departingfrom the scope of the invention.

In addition to process 1100 for ranking toplinks, maintenance process900 preferably includes a process 1200 for ranking related Webrooms, asillustrated in FIG. 12A. As previously described in connection with step806 of process 800, each Webroom preferably has a database of relatedWebroom rating data 808. Database 808 preferably comprises rating andactivity information for each linked Webroom page, and for Webrooms thatare not linked but are otherwise identified as prospective Webrooms forlinking. At step 1202, rating and activity information is obtained fromdatabase 808. At step 1204, an aggregate score is computed for eachrating and activity category. As discussed in connection with process1000, aggregate scores may be derived using a variety of differentstatistical measures.

At step 1206, the Webroom pages are assigned a score in each rating andactivity category. At steps 1208 and 1214, Webroom pages that fail toachieve a predetermined minimum score in one or more categories areidentified and their links are removed from the toplist. Also at steps1208 and 1214, Webrooms that have newly achieved a predetermined minimumscore are linked to the Webroom undergoing maintenance. At step 1210,the linked Webrooms are ranked. Preferably, an overall (or default)ranking is determined for the linked Webrooms. Additionally, a rankingin one or more rating or activity categories may be determined forproviding users an option to view alternative rankings. For example,Webroom pages may be separately ranked according to their scores in arelevance category, or according to their popularity. Ranking ispreferably continuous, that is, Webrooms are preferably ranked in asequence. Whatever ranking system is used, it should be designed tofacilitate a central purpose of identifying the most closely related anduseful Webrooms. Webrooms that fail to meet minimum standards, which mayvary depending on the topics of other Webrooms linked to the Webroomundergoing maintenance, have their links removed. Standards may change,for example, when new Webrooms are created and linked that are focusedon narrower topics more closely related to the Webroom. For example, inan initial stage of evolution, a Webroom having a topic of “dogs” may belinked to a Webroom with a topic of “cats,” but as the Webroom systemevolves, and many more dog-specific Webrooms are created, the link tothe cat Webroom may be removed.

At step 1212, the page rank and scores are recorded in database 808. Atable 1220 exemplary of ranking and scoring data that may be recorded isprovided in FIG. 12B. Table 1220 comprises rows 1222 and columns 1224.Each row of rows 1222, for example, rows 1231-1232, is assigned to aunique Webroom. Each column, for example, columns 1241-1249, is assignedto a rating or activity category. It should be noted that table 1220contains a section of columns (e.g., columns 1241-1242 and 1244-1249)for data pertaining to a particular related Webroom, and another sectionof columns (e.g., column 1243) for general related Webroom data, such asnumber of related Webroom member users. Each Webroom will have differentdata in its own table 1220, reflecting that Webrooms are rated withrespect to their relationship to other Webrooms. Exemplary data isprovided in each cell of the table 1220 to illustrate how differentrating and activity information may be used to classify pages.

For example, column 1241 contains a relatedness rank, and column 1242contains a measurement of the number of times the related Web room hasbeen linked to A column (not shown) may additionally be provided for acount of the number of votes received, that is, the number of times theWebroom has been rated as related to its target Webroom by its users.Column 1243 contains a count of the number of members for each relatedWebroom. Columns 1244 through 1246 contain each page's aggregate scorein the respective categories of relevance, depth, and breadth. Column1247 contains a count of the number of posts in the Webroom. Column 1248contains a classification optionally assigned to each Webroom on thebasis of other information in the table. Column 1249 contains theWebroom rank relative to other linked Webrooms in the sameclassification.

A comparison of the Webrooms is made using the exemplary data. Row 1231pertains to Webroom1, showing relatively high relevance and depth ofinformation, but relatively low rating for breadth of information(indicating the posts are narrowly focused on the topic, which promotesgood topical organization). Accordingly, Webroom1 has a relatively highrank of nine. Also, Webroom1 is classified as an “Academic” Webroom, andis ranked fifth in its classification. Data for Webroom2 is shown on row1232. Webroom2 has a relatively high level of activity, and goodrelevance, but a low depth rating with a corresponding high breadthrating, indicating a poor focus on the topic and relatively littleinformation. Accordingly, Webroom2 has a low ranking of fifty-six.However, Webroom2 is classified as a children's page, and has arelatively higher rank of ten in its own class, indicating that it maybe of interest to children. One skilled in the art will recognize fromthe foregoing example that a wide variety of rating and activity datamay be recorded, and used to classify and rank Webrooms in numerousways, without departing from the scope of the invention.

It should be generally noted that the topical focus of Webrooms willchange over time, and thus relationships between Webrooms is subject tochange. Therefore, users preferably rate related Webrooms (and relatedWeb pages and posts) continually. Also, the weight of rating informationis preferably related to its age. That is, older information is of lessvalue for rating purposes. In preferred embodiments of the invention,rating data is time stamped, and is analyzed on a variety of time framesand other measures of duration. For example, data may be analyzed onlyfor the past week, month, 100 votes, 5000 accesses, 2000 posts, and soforth. Thus, data received prior to the selected duration measure wouldbe discounted or discarded for the purpose of determining currentrankings

Webrooms which do not achieve a necessary minimum ranking and thus arenot listed as related, are also subject to change in topical focus andmay, at some future point, become related. Thus, in one preferredembodiment, a Webroom that fails to become listed as related is held insuspense for an appropriate period of time, and once the time haspassed, the Webroom can again be nominated as related to the Web roomfor which the relation ranking had previously failed. The durationmeasures may be increased based on the number of such failednominations. For example, if a Webroom (A) has been nominated and failedto be voted as related to another Webroom (B) on several occasions, thatWebroom (A) may need to wait much longer before it can again benominated as related to Webroom (B), although it may immediately benominated as related to Webroom (C). One skilled in the art willrecognize that other variations on determining related Webrooms arepossible, without departing from the scope of the invention.

Preferably, selected Webroom rating information may be viewed by Webroomusers. For example, Webroom directory 1260 is preferably provided onroot menu page 570, as illustrated in FIG. 12C. Menu 1260 preferablycontains a directory 1264 of Webrooms. The directory may be presented invarious formats, such as a tree format as depicted in FIG. 12C, or as alist in a ranked order (not shown). A user preferably may selectdifferent formats using a selection tool, such as format button 1262.Each entry in the directory 1264 preferably comprises a hyperlink 1261to its related Webroom page, and is preferably provided with a hyperlink1262 to a Webroom information page 1270. Information page 1270 ispreferably provided with graph 1274 or other presentation of Webroomactivity and rating information, and specific information, such as topic1273, average use level 1275, founder identity 1276, age 1277, andprogeny (spun off Webrooms) 1278. Additionally, page 1270 preferablyincludes a hyperlink 1279 to directory page 1260. Directory 1260 mayadditionally include scrolling tools for scrolling through the directory(not shown).

Returning to FIG. 9, after completion of the processes for rankingusers, related Web pages, and related Webrooms have been completed, atstep 904, the Webroom pages are regenerated to reflect any changes inuser, toplist, or Webroom rankings. At step 906, the databases of posts616, post ratings 608, and page ratings 708 are searched to identifyrelated topics in the postings or linked Web pages. The search 906 mayuse rating patterns to identify groups of postings or linked pageshaving relatively low relevance rankings, but relatively high rankingsin other categories, such as activity, that reflect user interest. Anygroups of pages and postings with these rating patterns are searched toidentify common keywords. If a common set of repeated keywords isidentified, at step 908, a determination of whether the postings relateto a new topic is made. Preferably, the determination is made with thehelp of a user, such as the founding user, or some other person with aninterest in the Webroom and competent for making a topic determination.Various guidelines and predetermined criteria may be used to guidedecisions on whether a new topic is present, using similarconsiderations as discussed above with respect to step 416 of process400 (founding a Webroom).

If a new topic is identified, at step 910, a determination of whether tofound a new Webroom with the new topic, or divide the existing Webroom,is made. Again, this determination is preferably made with assistancefrom a human operator, using automatically generated data revealing theprospective new topic. If the posts and other information relating tothe new topic can easily be separated from the existing Webroom, at step912, the Webroom is divided in two, with one part retaining the oldtopic (or the old topic modified by subtraction of the new topic) alongwith its related information, and the other part assuming the new topicand its related information. In the case of Webroom division, the twonew Web rooms begin with the same user base as the original Webroom, andgradually evolve distinct user sets.

It should be noted that Webrooms with identical topics may be readilymerged, and the division process may lead to separate Web rooms withidentical topics. For example, if the new topic is separable from theoriginal Webroom, but already covered by a second existing Webroom, theinformation pertaining to the new topic is preferably removed from theoriginal Webroom and merged into the second Webroom. In this event, themember users of the original Webroom are also added to the secondWebroom. Any newly divided or merged Webrooms are then processedbeginning at step 902 of the maintenance process 900. If at step 910 itis determined that the Webroom may not be divided because the posts andpages pertaining to the new topic also contain information pertaining tothe original topic, then a new Webroom is preferably created for the newtopic using a method 400 as discussed above, and the original Webroomresumes the maintenance process at step 914.

At step 914, the activity scores of the Webroom as a whole are analyzedand compared to predetermined criteria, to determine if enough activityexists to warrant remaining active. If it is determined at step 916 thatthere is insufficient activity, the Webroom goes into hibernation atstep 918, meaning that its databases are archived and the Webroom isinactivated until a renewed interest in the Webroom topic “awakens” itfrom hibernation. Conversely, if sufficient activity is found, then theWebroom resumes normal operation until the next maintenance cycle 900 isinitiated at step 902. Thus, the foregoing process 900 provides forpreserving and increasing the topical organization of the Webroomsystem, and of individual Webrooms within the system, even as the amountof information in the Webroom system grows.

Users are preferably provided with an option to customize' theirinterface with Webroom content by specifying preferences for filteringWebroom posts using post rating data, according to a process 1300illustrated in FIG. 13A. At step 1302, user preferences are receivedfrom a user. Preference data may be obtained using a preference form,such as form 1340 illustrated in FIG. 13B. Preference information ispreferably gathered at the time a user registers for Webroom access, andmay be changed at any time upon request of the user.

Form 1340 preferably has various data entry fields for enteringpreference data, including a keyword field 1342, an author field 1344, aseries of post rating fields 1346, a series of user rating fields 1348,and date fields 1350. Any combination of the fields may be selected. Forexample, using the keyword field 1342, the user can specify one or morephrases or keywords for filtering the posts. Similarly, the user canrestrict posts by author, by post rank or score, by rank or score of thepost authors, or by date, using the aforementioned fields. Additionalfields may be provided for filtering posts by any criteria that ismeasured. Preferably, preferences may be expressed as Booleanexpressions, for example, “cat AND NOT dog,” as is known in the art forpermitting complex queries. In the alternative to form 1340, arelatively small tolerance bar 670 may be provided adjacent to theposts, as illustrated in FIG. 6B, for permitting filtering bypreferences that may readily be modified. It is anticipated thatfiltering posts by user preferences will greatly enhance the utility ofprior art information exchange groups. By specifying preferences, userswill be able to quickly view those portion of the posts that pertain totheir specific interests. Users are also able to prevent the display ofposts that they find offensive or uninteresting, such as flames andspam. At the same time, other users who are interested in viewing suchposts are able to do so by specifying different preference information.One skilled in the art will recognize that various methods may be usedfor obtaining user preferences without departing from the scope of theinvention.

For example, in an embodiment of the invention pertaining to Webroomswhich provide for exiling of members, a default user preference iscreated for tolerance of exiled members. Users are permitted to changethis default preference to increase or decrease their tolerance forviewing posts by other members who have had posts rated to be spam,flames or otherwise inappropriate. Thus, a member may be exiled from thevast majority of the group, but viewers who have set a high tolerancefor the offense resulting in the exile would nevertheless be able toview posts by the offending member.

Referring again to FIG. 13A, at step 1305, the user preferences arestored in a database 1308. At step 1306, a portion of the Webroom postsare obtained from post database 616 and tested against the preferencethreshold criteria at step 1312. Posts which do not meet the thresholdcriteria are rejected (filtered) at step 1314, and at steps 1316 and1310, steps 1312 and 1314 are repeated until all desired posts have beenfiltered. At step 1320, the filtered posts are displayed to the user ina manner customary for Web rooms.

The present invention preferably provides for establishment of privateWebrooms. Private Webrooms are restricted to specified users, butotherwise operate like Webrooms described above, as illustrated by FIG.14, providing for organized, private messaging. Private Webroom process1400 comprises a first step 1402 of receiving a request for a privateWebroom. At step 1404, a Webroom is founded according to the process 400illustrated in FIG. 4A, but specifying a private topic and a group ofpermitted users. It should be noted that private Webrooms for distinctuser groups are preferably permitted to have duplicate topics, unlikepublic Webrooms. At step 1408, the specified users are notified that theprivate Webroom is open for operation. At step 1408, the private Webroomis operated and maintained like a public Webroom, except that access isrestricted to the specified users.

In an embodiment of private Webrooms, a messaging function is performed.For example, a user request for a private Webroom with specified userscan cause a scrolling bar to be displayed across the top of any Webroompage viewed by the specified users which states “You have a privatemessage.” Each specified user can click on the notice, which directs theuser to the private Webroom where the requesting user's message islocated. Access to the Webroom is limited to the requesting user and thespecified sender. In this manner, users can receive messages withoutposting their e-mail address, or without having an e-mail account. Tothey extent that it is desired, private Webroom users may also make useof the organizing features of regular Webrooms.

Additionally, as previously described in connection with FIG. 6B, ane-mail forwarding method is preferably provided to allow directe-mailing between members, without requiring members to publiclydisclose their e-mail address. In preferred embodiments, members providetheir e-mail address at the time of registration. The member e-mailaddresses are stored in a secure, private database by a Webroom mailserver. Each post 676 of the Webroom pages 650 preferably includes ane-mail button 674, as previously described. To send an e-mail message toanother member, a member may open a post authored by the desiredrecipient, and select the button 674 (or other command feature). In analternative embodiment, a private e-mail function is accessed byselecting a member name from a member list. After the function isaccessed, a messaging window is provided in which the desired messagemay be entered. The entered message is then forwarded to the intendedrecipient at the recipient's private address, without disclosing theaddress to the sender.

As a further privacy feature, the present invention provides forcontrolling terminals to conceal private information from, other Webroomusers, according to a method 1500 illustrated in FIG. 15. At 1502, theWebroom system receives a request for terminal control from a user. Forexample, a supervising user, such as a parent, registers for a parentalcontrol by providing the phone numbers, names, addresses, or any otherprivate information that the supervising user does not wish revealed,for example, by a child. The Webroom software then stores the privateinformation in a database 1506 at step 1504. Control software is set upat step 1508 that automatically filters posts by any user of thatterminal, unless an appropriate password is entered to disable thefilter. The software operates by intercepting messages from the terminalat step 1510, and parsing the messages looking for private information(including misspellings and abbreviations of private information) atstep 1512. If any private information is found at step 1514, then themessage is altered to conceal the private information by replacing itwith a substituted string at step 1516. The altered message is then sentto the Webroom server in the usual manner at step 1518.

Method 1500 preferably operates so that the terminal, e.g., a child'scomputer, properly displays the information as provided by the child,however, an altered string that contains no sign of alteration is sentto the server, and therefore, the Webroom community. For example, “123”and “Green Street” are designated as control strings by a parent of achild user named “Josh”, and the substituted strings are “141” and“Spring Street.” In this instance, an exchange between Josh and anotheruser would be as follows:

User: What is your address, little boy?

Josh responds and his screen displays: “My address is 123 Green Street.”

The server receives and broadcasts: “My address is 141 Spring Street.”In this instance, a potentially undesirable user has not received anyuseful information. In another preferred embodiment, the information isscrambled in line through the use of a public key/private key modality,such as PGP software.

Having thus described a preferred embodiment of Webrooms, it should beapparent to those skilled in the art that certain advantages of thewithin system have been achieved. It should also be appreciated thatvarious modifications, adaptations, and alternative embodiments thereofmay be made within the scope and spirit of the present invention. Forexample, a method for providing a computer-implemented, topicallyorganized self-evolving exchange group on a wide area network has beenillustrated, but it should be apparent that the inventive conceptsdescribed above would be equally applicable to other informationexchange groups on wide area networks. The invention is further definedby the following claims.

1. A method for concealing private information exchanged between users,the method comprising: intercepting, by a computing device, an originalmessage sent from a first user to a second user, the original messagecontaining information associated with the first user; accessing, by acomputing device, a data structure storing private informationassociated with respective users in order to identify privateinformation associated with the first user; locating, by a computingdevice, any of the identified private information associated with thefirst user in the original message; generating, by a computing device,an altered message by concealing at least a portion of the locatedprivate information; and sending the altered message to the second user.2. The method of claim 1, further comprising concealing evidence ofgenerating the altered message.
 3. The method of claim 1, wherein theprivate information associated with respective users comprises at leastone of a phone number, an address, and a name of respective users. 4.The method of claim 1, wherein concealing the located privateinformation comprises replacing at least a portion of the locatedprivate information with a substituted string.
 5. The method of claim 4,wherein the substituted string comprises information of the same type asthe located private information.
 6. The method of claim 4, wherein thesubstituted string comprises located private information that has beenencrypted.
 7. The method of claim 1, further comprising displaying theoriginal message to the first user without alteration.
 8. The method ofclaim 1, wherein the identified private information is provided by athird user.
 9. A method for private communication between users of aninformation exchange group, the method comprising: authorizing one ormore users for access to an information exchange group; receiving, by acomputing device, a private electronic address for a first authorizeduser; receiving, by a computing device, a request from a secondauthorized user via one or more user interfaces of the informationexchange group to direct a message to the first authorized user;receiving, by a computing device, content for the message from thesecond authorized users via one or more user interfaces of theinformation exchange group; and sending, by a computing device, themessage, including the content received from the second authorized user,to the private electronic address of the first authorized user, whereinthe private electronic address of the first authorized user is notrevealed to the second authorized user.
 10. The method of claim 9,wherein the private electronic address of the first user comprises anelectronic mail address.
 11. The method of claim 10, wherein receivingthe request from the second authorized user comprises receiving aselection of a user interface object within another message authored bythe first authorized user within the information exchange group.
 12. Themethod of claim 9, wherein receiving the request from the secondauthorized user comprises receiving a selection of the first authorizeduser from a list of authorized users of the information exchange group.13. A method for rank ordering a list of links on a Web page, the methodcomprising: measuring, by a computing device, an amount of traffic to orfrom a first Web page generated by respective other Web pages, whereinthe first Web page includes links to at least some of the other Webpages; assigning, by a computing device, a rank for respective links ofthe first Web page according to the respective amounts of trafficgenerated by the other Web pages corresponding to the links; andordering the links on the first Web page according to the respectiveassigned ranks.
 14. The method of claim 13, wherein the amount oftraffic comprises at least one of: a number of times the first Web pageis requested from the respective other Web pages; and a number of timesthe respective other Web pages are requested by accessing the links ofthe first Web page.
 15. The method of claim 13, further comprisingreceiving one or more ratings for the first Web page from users visitingthe first Web page.
 16. The method of claim 15, wherein the one or moreratings each comprise one or more categories.
 17. The method of claim15, further comprising assigning the rank to respective links of thefirst Web page according to the respective amounts of traffic and theone or more ratings for the first Web page.
 18. The method of claim 13,further comprising removing respective links having a rank less than afirst selected value from the first Web page to a second Web page. 19.The method of claim 18, further comprising removing respective linkshaving a rank less than a second selected value from the second Webpage.